Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 390a3e08688d95a00ce19d40692c2d9f6d32fc8601db4c65271128861ff0da9d

Tx prefix hash: 5e7c5d2df123a539bc834e247c2a860433992a846b423ba1ccd5d9246e8e13e4
Tx public key: ca38b4e4457d58e91d118ebe5676d70b36f663e8cf29d2795820c7c831e0e97f
Timestamp: 1716936497 Timestamp [UCT]: 2024-05-28 22:48:17 Age [y:d:h:m:s]: 00:228:02:09:49
Block: 1032154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163243 RingCT/type: yes/0
Extra: 01ca38b4e4457d58e91d118ebe5676d70b36f663e8cf29d2795820c7c831e0e97f0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28d36935fcaccd8abd30dcb1b4c9016fd5588839bf6efdd2e543c3171115a9ac 0.600000000000 1500603 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": 1032164, "vin": [ { "gen": { "height": 1032154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28d36935fcaccd8abd30dcb1b4c9016fd5588839bf6efdd2e543c3171115a9ac" } } ], "extra": [ 1, 202, 56, 180, 228, 69, 125, 88, 233, 29, 17, 142, 190, 86, 118, 215, 11, 54, 246, 99, 232, 207, 41, 210, 121, 88, 32, 199, 200, 49, 224, 233, 127, 2, 17, 0, 0, 0, 5, 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