Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d170ab1c4a21fad24e27a25427a475df6fdb12470e00e80c62edda438829c6a

Tx prefix hash: ed4f7838566566a3bb45b0bc025022f61f9c5a393805eb2c1fb1d69cd176d50e
Tx public key: a619b0b634776a95cf81295dcc09aec60e0ccc9015418caa89a57d219c86ad3e
Timestamp: 1713901902 Timestamp [UCT]: 2024-04-23 19:51:42 Age [y:d:h:m:s]: 00:358:14:41:39
Block: 1006995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256364 RingCT/type: yes/0
Extra: 01a619b0b634776a95cf81295dcc09aec60e0ccc9015418caa89a57d219c86ad3e0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b9e2ead9a0f15712fdd8c3c38f3596b99afc3dd5a8736ba1eda10df0109a713 0.600000000000 1468201 of 15

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": 1007005, "vin": [ { "gen": { "height": 1006995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b9e2ead9a0f15712fdd8c3c38f3596b99afc3dd5a8736ba1eda10df0109a713" } } ], "extra": [ 1, 166, 25, 176, 182, 52, 119, 106, 149, 207, 129, 41, 93, 204, 9, 174, 198, 14, 12, 204, 144, 21, 65, 140, 170, 137, 165, 125, 33, 156, 134, 173, 62, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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