Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc255eeb5591e207f72da28219280b42457e1953f274f7b7b44132eb895a6f0a

Tx prefix hash: 40975610054e0f7ecc567e2f5633bb73a100f4d3cdb756f661ea08e26d3727e3
Tx public key: d0f117789c39020f4b552c2faafecc9ea3f24e6bcc5bb9dd397b538cf51c4eec
Timestamp: 1705450243 Timestamp [UCT]: 2024-01-17 00:10:43 Age [y:d:h:m:s]: 01:157:19:58:35
Block: 936905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373744 RingCT/type: yes/0
Extra: 01d0f117789c39020f4b552c2faafecc9ea3f24e6bcc5bb9dd397b538cf51c4eec0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db5b5a3629fd1a564f10ecb27d54ca62c70c2eb384e20ac114354b0805504ea2 0.600000000000 1394947 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": 936915, "vin": [ { "gen": { "height": 936905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db5b5a3629fd1a564f10ecb27d54ca62c70c2eb384e20ac114354b0805504ea2" } } ], "extra": [ 1, 208, 241, 23, 120, 156, 57, 2, 15, 75, 85, 44, 47, 170, 254, 204, 158, 163, 242, 78, 107, 204, 91, 185, 221, 57, 123, 83, 140, 245, 28, 78, 236, 2, 17, 0, 0, 0, 8, 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