Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 878f7c04c41977e89ffd1c5965891e64e4736c66651392151c4bebd256e76e08

Tx prefix hash: d2629b170561d405cb9bd29c492c4e7ca8db3da7bb1fdc23474c901df0be6774
Tx public key: 490b08ed940c8cfbf28c3a56f6cf4f5fc0aa6d2eac75de7ac752aeec2c9e17a8
Timestamp: 1635274684 Timestamp [UCT]: 2021-10-26 18:58:04 Age [y:d:h:m:s]: 03:064:22:41:49
Block: 361037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 824837 RingCT/type: yes/0
Extra: 01490b08ed940c8cfbf28c3a56f6cf4f5fc0aa6d2eac75de7ac752aeec2c9e17a80211000000144f792ffd000000000000000000

1 output(s) for total of 39.060244084000 dcy

stealth address amount amount idx
00: bb6f1f1f752f1c2c8da892a1359ac0b0fc9e30bb7c4fecdf0e68511a8fba20d3 39.060244084000 734666 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": 361047, "vin": [ { "gen": { "height": 361037 } } ], "vout": [ { "amount": 39060244084, "target": { "key": "bb6f1f1f752f1c2c8da892a1359ac0b0fc9e30bb7c4fecdf0e68511a8fba20d3" } } ], "extra": [ 1, 73, 11, 8, 237, 148, 12, 140, 251, 242, 140, 58, 86, 246, 207, 79, 95, 192, 170, 109, 46, 172, 117, 222, 122, 199, 82, 174, 236, 44, 158, 23, 168, 2, 17, 0, 0, 0, 20, 79, 121, 47, 253, 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