Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dad4c4e36fcaf861251d7f09fc83b685d385a206795ca3ac3576437aa86702d

Tx prefix hash: 966c8f96c75f9adb54df511ef5b4b5258190469ff73012c3a4c8c46a05203c1a
Tx public key: 883432558e831768432a0aee90e1f1921bf5843d9cf0a29299e2ac44beb6af74
Timestamp: 1577696801 Timestamp [UCT]: 2019-12-30 09:06:41 Age [y:d:h:m:s]: 05:042:01:37:06
Block: 34895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1179843 RingCT/type: yes/0
Extra: 01883432558e831768432a0aee90e1f1921bf5843d9cf0a29299e2ac44beb6af7402110000000ad81c26c0000000000000000000

1 output(s) for total of 470.304608613000 dcy

stealth address amount amount idx
00: dc2f3d7a355672d503e95daaf4f11a6cddb9c3eeb228e892d0b6029f11c1ade4 470.304608613000 58788 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": 34905, "vin": [ { "gen": { "height": 34895 } } ], "vout": [ { "amount": 470304608613, "target": { "key": "dc2f3d7a355672d503e95daaf4f11a6cddb9c3eeb228e892d0b6029f11c1ade4" } } ], "extra": [ 1, 136, 52, 50, 85, 142, 131, 23, 104, 67, 42, 10, 238, 144, 225, 241, 146, 27, 245, 132, 61, 156, 240, 162, 146, 153, 226, 172, 68, 190, 182, 175, 116, 2, 17, 0, 0, 0, 10, 216, 28, 38, 192, 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