Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36a437511932cfc2f3c0ccd5da0ae1e1bcd7ea897d7c54860668030163c084b1

Tx prefix hash: 0641856a06fbc03f20ca4fba6cbb5bc476f3f0be9d01023b828bc9e007c12f52
Tx public key: 913d891149c5e2af54a6335d5ceb0068741e7b40310cfa0f1b3cec39c31c6476
Timestamp: 1711080142 Timestamp [UCT]: 2024-03-22 04:02:22 Age [y:d:h:m:s]: 00:311:00:05:34
Block: 983621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222365 RingCT/type: yes/0
Extra: 01913d891149c5e2af54a6335d5ceb0068741e7b40310cfa0f1b3cec39c31c647602110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95db8e88321a7d594e89e0878fdb822b2c1c3892103fc464b1dcbc92a7333826 0.600000000000 1443762 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": 983631, "vin": [ { "gen": { "height": 983621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95db8e88321a7d594e89e0878fdb822b2c1c3892103fc464b1dcbc92a7333826" } } ], "extra": [ 1, 145, 61, 137, 17, 73, 197, 226, 175, 84, 166, 51, 93, 92, 235, 0, 104, 116, 30, 123, 64, 49, 12, 250, 15, 27, 60, 236, 57, 195, 28, 100, 118, 2, 17, 0, 0, 0, 14, 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