Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90bcea5f7ea57b0a141031dfbe2d40d81901f214c57feea42e8548610964c3f6

Tx prefix hash: da04caee1363c9b14b518f8e54fe6b3536271f85533a269edabaf43e1a9088bb
Tx public key: 0b6da94f242da533fdc948addc093902f16796c0b36e5d7cc81a6eb91f64036e
Timestamp: 1704575417 Timestamp [UCT]: 2024-01-06 21:10:17 Age [y:d:h:m:s]: 01:159:19:38:12
Block: 929659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375303 RingCT/type: yes/0
Extra: 010b6da94f242da533fdc948addc093902f16796c0b36e5d7cc81a6eb91f64036e02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 806c68047602e7af34e027ffefa9d2959089254458eb235de3d00fc815f93039 0.600000000000 1387535 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": 929669, "vin": [ { "gen": { "height": 929659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "806c68047602e7af34e027ffefa9d2959089254458eb235de3d00fc815f93039" } } ], "extra": [ 1, 11, 109, 169, 79, 36, 45, 165, 51, 253, 201, 72, 173, 220, 9, 57, 2, 241, 103, 150, 192, 179, 110, 93, 124, 200, 26, 110, 185, 31, 100, 3, 110, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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