Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9eceb5bc8156b2851aff145df005e77e9b5a86044a0009f2ea974ddb627e411

Tx prefix hash: 6710e5b691ce152b5c5a2f84beae3e92bc21bd6a849d245a6943f38ca1e5bdee
Tx public key: 031ca6ff6d086f84813d9bd902f143bad3eb953c3c861ac20257594dfe24e72f
Timestamp: 1734612864 Timestamp [UCT]: 2024-12-19 12:54:24 Age [y:d:h:m:s]: 00:106:07:29:49
Block: 1178615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75735 RingCT/type: yes/0
Extra: 01031ca6ff6d086f84813d9bd902f143bad3eb953c3c861ac20257594dfe24e72f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e50a70c616c2c0666117a6361d331cf9930d59e61907b9e64528dda48cd2f9cb 0.600000000000 1665004 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": 1178625, "vin": [ { "gen": { "height": 1178615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e50a70c616c2c0666117a6361d331cf9930d59e61907b9e64528dda48cd2f9cb" } } ], "extra": [ 1, 3, 28, 166, 255, 109, 8, 111, 132, 129, 61, 155, 217, 2, 241, 67, 186, 211, 235, 149, 60, 60, 134, 26, 194, 2, 87, 89, 77, 254, 36, 231, 47, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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