Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8abb2f050e1f202b430645c67b767c6ba83047d1082b44d735f99c05ea5a49f

Tx prefix hash: 2c37719e1bfe373d19c2c2ded5ab5a626a3412944159d407094a7002b7bcc23c
Tx public key: 5ecead127db3fcf29327a9492f5ff8dafbb420baba216368f7b3a4ea3c01c043
Timestamp: 1726440677 Timestamp [UCT]: 2024-09-15 22:51:17 Age [y:d:h:m:s]: 00:116:16:49:00
Block: 1110946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83457 RingCT/type: yes/0
Extra: 015ecead127db3fcf29327a9492f5ff8dafbb420baba216368f7b3a4ea3c01c04302110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2570455e7ebaaf2d695827934d0c6180e7a0718a68e9aa4e3189767ac059177e 0.600000000000 1589735 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": 1110956, "vin": [ { "gen": { "height": 1110946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2570455e7ebaaf2d695827934d0c6180e7a0718a68e9aa4e3189767ac059177e" } } ], "extra": [ 1, 94, 206, 173, 18, 125, 179, 252, 242, 147, 39, 169, 73, 47, 95, 248, 218, 251, 180, 32, 186, 186, 33, 99, 104, 247, 179, 164, 234, 60, 1, 192, 67, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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