Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ad7fe4f9db1da6740916178d7962c2b1c4934e9f5661f4c357cfb41f36b637

Tx prefix hash: 11d41e8e055d05282aa4b90853e8016801e00319483daaee9d7370e90f0823d0
Tx public key: f9db9fa791a13e92f3f8c8d09f343479fab2a130ebcd58c7b83d304a4004443a
Timestamp: 1730905491 Timestamp [UCT]: 2024-11-06 15:04:51 Age [y:d:h:m:s]: 00:000:17:41:08
Block: 1147885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528 RingCT/type: yes/0
Extra: 01f9db9fa791a13e92f3f8c8d09f343479fab2a130ebcd58c7b83d304a4004443a021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bccc8f997768a56b8cda64d065124c23923a504ecbe727f004cf3431a67e3113 0.600000000000 1632594 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": 1147895, "vin": [ { "gen": { "height": 1147885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bccc8f997768a56b8cda64d065124c23923a504ecbe727f004cf3431a67e3113" } } ], "extra": [ 1, 249, 219, 159, 167, 145, 161, 62, 146, 243, 248, 200, 208, 159, 52, 52, 121, 250, 178, 161, 48, 235, 205, 88, 199, 184, 61, 48, 74, 64, 4, 68, 58, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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