Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0bef48eec49c8cab4fc4af3f8f25f3a01cf66d12b7c9ac18981d530fe8a6ae2

Tx prefix hash: 50677d66fa5d549f0bfdfacf94f3c85d17e1b5960c84b388097e64b728e325cf
Tx public key: dc0355e83cb4c5861863d848b7e68115de9b2556798dc95486c17566a7be5cd8
Timestamp: 1648511361 Timestamp [UCT]: 2022-03-28 23:49:21 Age [y:d:h:m:s]: 03:217:21:09:30
Block: 468532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 933650 RingCT/type: yes/0
Extra: 01dc0355e83cb4c5861863d848b7e68115de9b2556798dc95486c17566a7be5cd8021100000001d3fcec30000000000000000000

1 output(s) for total of 17.201219537000 dcy

stealth address amount amount idx
00: 6bb6eb999a63c014baea8491a66faaed7c54f77b4a04cf3d161e20db4ba92552 17.201219537000 887270 of 0

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": 468542, "vin": [ { "gen": { "height": 468532 } } ], "vout": [ { "amount": 17201219537, "target": { "key": "6bb6eb999a63c014baea8491a66faaed7c54f77b4a04cf3d161e20db4ba92552" } } ], "extra": [ 1, 220, 3, 85, 232, 60, 180, 197, 134, 24, 99, 216, 72, 183, 230, 129, 21, 222, 155, 37, 86, 121, 141, 201, 84, 134, 193, 117, 102, 167, 190, 92, 216, 2, 17, 0, 0, 0, 1, 211, 252, 236, 48, 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