Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0cc85dfa3b8964afd6f2429ea7164c18af01fe0d3706c3ef4442940ec05d478

Tx prefix hash: cde637b6fd59133074104c944abb5e62ad86d834a35df695a1d447126da1e6fc
Tx public key: c17b39a39913513d0e0e6b8a640850f96a0feb953187fc0ca2290519e44701c3
Timestamp: 1577126370 Timestamp [UCT]: 2019-12-23 18:39:30 Age [y:d:h:m:s]: 05:317:08:20:25
Block: 30061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1374439 RingCT/type: yes/0
Extra: 01c17b39a39913513d0e0e6b8a640850f96a0feb953187fc0ca2290519e44701c3021100000054d81c26c0000000000000000000

1 output(s) for total of 488.014919026000 dcy

stealth address amount amount idx
00: ff1f6ddb68764f0c1dbca58cc94716595e43897c1d8de4372325067e2536c748 488.014919026000 49629 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": 30071, "vin": [ { "gen": { "height": 30061 } } ], "vout": [ { "amount": 488014919026, "target": { "key": "ff1f6ddb68764f0c1dbca58cc94716595e43897c1d8de4372325067e2536c748" } } ], "extra": [ 1, 193, 123, 57, 163, 153, 19, 81, 61, 14, 14, 107, 138, 100, 8, 80, 249, 106, 15, 235, 149, 49, 135, 252, 12, 162, 41, 5, 25, 228, 71, 1, 195, 2, 17, 0, 0, 0, 84, 216, 28, 38, 192, 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