Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0b5a4b4af1e88cfbba15740e7c6dd982fe6fb1e13414021752c3c262d07ad65

Tx prefix hash: ca9a7ca3001b47a4235316efdf704702444e9a8893fe68b63cbcebb8462c0b10
Tx public key: a37f60740ced2ecd4ad051d8c134de7f8dca3d06d0079893e0812be758cace7d
Timestamp: 1709102551 Timestamp [UCT]: 2024-02-28 06:42:31 Age [y:d:h:m:s]: 01:280:20:20:39
Block: 967218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459492 RingCT/type: yes/0
Extra: 01a37f60740ced2ecd4ad051d8c134de7f8dca3d06d0079893e0812be758cace7d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9445427aeb62ae45d8b7f98f1063d0fa28de10ae84f21019cb60e85cf7a69f91 0.600000000000 1426989 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": 967228, "vin": [ { "gen": { "height": 967218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9445427aeb62ae45d8b7f98f1063d0fa28de10ae84f21019cb60e85cf7a69f91" } } ], "extra": [ 1, 163, 127, 96, 116, 12, 237, 46, 205, 74, 208, 81, 216, 193, 52, 222, 127, 141, 202, 61, 6, 208, 7, 152, 147, 224, 129, 43, 231, 88, 202, 206, 125, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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