Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c241ce8debf562f58f1cad4b8d9fbf44ff5c7544337d6016959a79d25e065554

Tx prefix hash: 639a02d0f248bd3ef4b1627ab2f6f582ed02e65fa4d14575bdcd9397a9eb116e
Tx public key: f0702c4b0a920f9b878e834ce97a6835fc305028eac00796a370f4980b2d00dc
Timestamp: 1580319595 Timestamp [UCT]: 2020-01-29 17:39:55 Age [y:d:h:m:s]: 04:302:10:33:57
Block: 54876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106998 RingCT/type: yes/0
Extra: 01f0702c4b0a920f9b878e834ce97a6835fc305028eac00796a370f4980b2d00dc0211000000094943cd9f000000000000000000

1 output(s) for total of 403.834913532000 dcy

stealth address amount amount idx
00: 03a41c241598c0e2b044ced5ac820902e75b015a0daedaa39d9387a5d42d99af 403.834913532000 101454 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": 54886, "vin": [ { "gen": { "height": 54876 } } ], "vout": [ { "amount": 403834913532, "target": { "key": "03a41c241598c0e2b044ced5ac820902e75b015a0daedaa39d9387a5d42d99af" } } ], "extra": [ 1, 240, 112, 44, 75, 10, 146, 15, 155, 135, 142, 131, 76, 233, 122, 104, 53, 252, 48, 80, 40, 234, 192, 7, 150, 163, 112, 244, 152, 11, 45, 0, 220, 2, 17, 0, 0, 0, 9, 73, 67, 205, 159, 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