Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dcd1dc82465000219480d855c80b702c841b59535d48d837e21b58d947c69f0

Tx prefix hash: 2f8c7f6d00ca90d2f11637b623b7860bb6695027df246aad96aaa33ac0cbf8b7
Tx public key: e4a8c6a02a8065eb5165117084ae852db93a76edbdec577bfe4c277822facfa8
Timestamp: 1694239861 Timestamp [UCT]: 2023-09-09 06:11:01 Age [y:d:h:m:s]: 01:214:04:38:33
Block: 844172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414196 RingCT/type: yes/0
Extra: 01e4a8c6a02a8065eb5165117084ae852db93a76edbdec577bfe4c277822facfa80211000000014b8f5122000000000000000000

1 output(s) for total of 0.979282056000 dcy

stealth address amount amount idx
00: 729e669f95c8dfb57043e930afeb1239ab8dcb1637b5f42d13841fe9ee53e1b9 0.979282056000 1297464 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": 844182, "vin": [ { "gen": { "height": 844172 } } ], "vout": [ { "amount": 979282056, "target": { "key": "729e669f95c8dfb57043e930afeb1239ab8dcb1637b5f42d13841fe9ee53e1b9" } } ], "extra": [ 1, 228, 168, 198, 160, 42, 128, 101, 235, 81, 101, 17, 112, 132, 174, 133, 45, 185, 58, 118, 237, 189, 236, 87, 123, 254, 76, 39, 120, 34, 250, 207, 168, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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