Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42d0132c2e4f6893a3f5cdde9de7424e345b32412eb6943572de4b824f7d9f17

Tx prefix hash: 99d3b938df21eaeb06217fdc990daf9a6443771ea0c6c7429f76cf07dd15211a
Tx public key: 9355eec795c9d09f9be5d5f66977f67936794c6207862a62b9b6256f1622da12
Timestamp: 1697201245 Timestamp [UCT]: 2023-10-13 12:47:25 Age [y:d:h:m:s]: 01:170:19:36:42
Block: 868745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383110 RingCT/type: yes/0
Extra: 019355eec795c9d09f9be5d5f66977f67936794c6207862a62b9b6256f1622da12021100000015e6d27f9c000000000000000000

1 output(s) for total of 0.811871341000 dcy

stealth address amount amount idx
00: 67d6d34f004c05d716e2768eeae6172156ab368406ece20f7d47b34af18701b7 0.811871341000 1323564 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": 868755, "vin": [ { "gen": { "height": 868745 } } ], "vout": [ { "amount": 811871341, "target": { "key": "67d6d34f004c05d716e2768eeae6172156ab368406ece20f7d47b34af18701b7" } } ], "extra": [ 1, 147, 85, 238, 199, 149, 201, 208, 159, 155, 229, 213, 246, 105, 119, 246, 121, 54, 121, 76, 98, 7, 134, 42, 98, 185, 182, 37, 111, 22, 34, 218, 18, 2, 17, 0, 0, 0, 21, 230, 210, 127, 156, 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