Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 059bfe4d4828e47ed4cf0347433e4316ab51896fe1c70beddf90917df14797fc

Tx prefix hash: d35dfff3c6116fe744bb1496f828ad46043eca9d90cd3dbf3d387cea88f3dc04
Tx public key: e8592599e5d1e36b2c8b05945e4d0b5dc83a7bd170bfb63f4f0a9bfcab87e65f
Timestamp: 1703873376 Timestamp [UCT]: 2023-12-29 18:09:36 Age [y:d:h:m:s]: 00:335:05:58:34
Block: 923853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240045 RingCT/type: yes/0
Extra: 01e8592599e5d1e36b2c8b05945e4d0b5dc83a7bd170bfb63f4f0a9bfcab87e65f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd794857e7d98c83c2af64b82899d1746df2aa837f2c41dd80a215d1ce11ebe6 0.600000000000 1381591 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": 923863, "vin": [ { "gen": { "height": 923853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd794857e7d98c83c2af64b82899d1746df2aa837f2c41dd80a215d1ce11ebe6" } } ], "extra": [ 1, 232, 89, 37, 153, 229, 209, 227, 107, 44, 139, 5, 148, 94, 77, 11, 93, 200, 58, 123, 209, 112, 191, 182, 63, 79, 10, 155, 252, 171, 135, 230, 95, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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