Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8ecd2081a3ba4647cb1f77090e3cb62bcfe3b690da882068de37e9937421c14

Tx prefix hash: c15abe446b9a469884ab906b05951051b940a9b81874569f164bbff58cc5b2aa
Tx public key: dd1eae101b51f915dbd2bf5e39a2b0fd4c22db1f7634a5c4196442433b59b7c6
Timestamp: 1719472736 Timestamp [UCT]: 2024-06-27 07:18:56 Age [y:d:h:m:s]: 00:279:01:35:38
Block: 1053175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199404 RingCT/type: yes/0
Extra: 01dd1eae101b51f915dbd2bf5e39a2b0fd4c22db1f7634a5c4196442433b59b7c60211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fda3683e3c95233716317613d495ea585763901d060892ca496ab6d48f5b6799 0.600000000000 1523522 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": 1053185, "vin": [ { "gen": { "height": 1053175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fda3683e3c95233716317613d495ea585763901d060892ca496ab6d48f5b6799" } } ], "extra": [ 1, 221, 30, 174, 16, 27, 81, 249, 21, 219, 210, 191, 94, 57, 162, 176, 253, 76, 34, 219, 31, 118, 52, 165, 196, 25, 100, 66, 67, 59, 89, 183, 198, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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