Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 413d46547af06e4b54533e09c5076f1423fc1a2b5fc4877ec699e0dc8467b99a

Tx prefix hash: 91aa8522105a5b82e17abcf995b4cfc9cbe5cf03e8d90b208a398e6f061b33c3
Tx public key: 965931ab49f5204f4bfc88091c48a0b362818677165d4239e52026ea2881e53e
Timestamp: 1578518540 Timestamp [UCT]: 2020-01-08 21:22:20 Age [y:d:h:m:s]: 05:056:14:04:18
Block: 41625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1190293 RingCT/type: yes/0
Extra: 01965931ab49f5204f4bfc88091c48a0b362818677165d4239e52026ea2881e53e02110000004317786bcf000000000000000000

1 output(s) for total of 446.765821084000 dcy

stealth address amount amount idx
00: a055ce88a6aedd6f26221cfe5e8e48973ce2b5e286d89a6ca99398875fd34692 446.765821084000 74304 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 41635, "vin": [ { "gen": { "height": 41625 } } ], "vout": [ { "amount": 446765821084, "target": { "key": "a055ce88a6aedd6f26221cfe5e8e48973ce2b5e286d89a6ca99398875fd34692" } } ], "extra": [ 1, 150, 89, 49, 171, 73, 245, 32, 79, 75, 252, 136, 9, 28, 72, 160, 179, 98, 129, 134, 119, 22, 93, 66, 57, 229, 32, 38, 234, 40, 129, 229, 62, 2, 17, 0, 0, 0, 67, 23, 120, 107, 207, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8