Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 333f1192238dca1601a8faa2ae260b4ae27439464bc76ca696eb6647daa0abb2

Tx prefix hash: cee921f8b3ef7439ff313592f496b78e8008791fed819ef61bd12b54ef7ecac7
Tx public key: 3de2f08e3c40e187cd8cbdbc23a4e7a284d286ecc841e81d01f7f7fd8dacb09f
Timestamp: 1659337674 Timestamp [UCT]: 2022-08-01 07:07:54 Age [y:d:h:m:s]: 03:096:00:41:29
Block: 556228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 848420 RingCT/type: yes/0
Extra: 013de2f08e3c40e187cd8cbdbc23a4e7a284d286ecc841e81d01f7f7fd8dacb09f02110000000175e3f0e9000000000000000000

1 output(s) for total of 8.810201836000 dcy

stealth address amount amount idx
00: 7286a3a2c1540b68484d2ac1e4140d1698025e8ccd7ae44f3b01398e6e42c05e 8.810201836000 988156 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": 556238, "vin": [ { "gen": { "height": 556228 } } ], "vout": [ { "amount": 8810201836, "target": { "key": "7286a3a2c1540b68484d2ac1e4140d1698025e8ccd7ae44f3b01398e6e42c05e" } } ], "extra": [ 1, 61, 226, 240, 142, 60, 64, 225, 135, 205, 140, 189, 188, 35, 164, 231, 162, 132, 210, 134, 236, 200, 65, 232, 29, 1, 247, 247, 253, 141, 172, 176, 159, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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