Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f37320be80f53e0a6e50c29b28b286e7ae15fef1f5a78dcf021f548cf8dc4e19

Tx prefix hash: 6fa34edcfbf5f49048e394c6a6caa324a6b32a700596822d5fca541c5d255de2
Tx public key: a18281aeb8758358871cf4b0e49b09297cb43ae18be5238e46a8ed951a01f49f
Timestamp: 1724263243 Timestamp [UCT]: 2024-08-21 18:00:43 Age [y:d:h:m:s]: 00:227:09:50:15
Block: 1092911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162381 RingCT/type: yes/0
Extra: 01a18281aeb8758358871cf4b0e49b09297cb43ae18be5238e46a8ed951a01f49f02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55436f0607fb1d71979fe038625f3273baf9a2109c94dd9f1618053ff8627c2d 0.600000000000 1567750 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": 1092921, "vin": [ { "gen": { "height": 1092911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55436f0607fb1d71979fe038625f3273baf9a2109c94dd9f1618053ff8627c2d" } } ], "extra": [ 1, 161, 130, 129, 174, 184, 117, 131, 88, 135, 28, 244, 176, 228, 155, 9, 41, 124, 180, 58, 225, 139, 229, 35, 142, 70, 168, 237, 149, 26, 1, 244, 159, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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