Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38c710b761c265857d8f644e049143f344ca741e2a22eb99312751cdc66e9394

Tx prefix hash: 9b385a822d0cce1a94e01790c9c7abcc7255453e3001719a92e4559ce0c3fb97
Tx public key: ce5f39653b0816037c34e846bcf5bd468dc3a85942ccd3ca9f062e3b992354f2
Timestamp: 1737167723 Timestamp [UCT]: 2025-01-18 02:35:23 Age [y:d:h:m:s]: 00:058:09:52:59
Block: 1199730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41539 RingCT/type: yes/0
Extra: 01ce5f39653b0816037c34e846bcf5bd468dc3a85942ccd3ca9f062e3b992354f20211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87f1b8e49e8f7f5a0dc027fbb1d7b0395eb81a9855d44152290e675235c6e2e1 0.600000000000 1686363 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": 1199740, "vin": [ { "gen": { "height": 1199730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87f1b8e49e8f7f5a0dc027fbb1d7b0395eb81a9855d44152290e675235c6e2e1" } } ], "extra": [ 1, 206, 95, 57, 101, 59, 8, 22, 3, 124, 52, 232, 70, 188, 245, 189, 70, 141, 195, 168, 89, 66, 204, 211, 202, 159, 6, 46, 59, 153, 35, 84, 242, 2, 17, 0, 0, 0, 1, 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