Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 269ec0747e36a2f26308aa9027a59592ab1409fae474222936fcaef8c3b9da06

Tx prefix hash: 85fd8ac2964d430620ae1b587fe78fa5b13bcecbb30ab7ed208ac599845a0dd2
Tx public key: b8f5a93e6b2b4c23487403ee2f36248045bdceca3315d5c31f56122d56e645be
Timestamp: 1724373027 Timestamp [UCT]: 2024-08-23 00:30:27 Age [y:d:h:m:s]: 00:238:15:02:47
Block: 1093822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170415 RingCT/type: yes/0
Extra: 01b8f5a93e6b2b4c23487403ee2f36248045bdceca3315d5c31f56122d56e645be021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c053ad0c727fa3d6ff743fe086a85a2d2edeafbefc37b7a5ee79288d2e38444 0.600000000000 1568843 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": 1093832, "vin": [ { "gen": { "height": 1093822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c053ad0c727fa3d6ff743fe086a85a2d2edeafbefc37b7a5ee79288d2e38444" } } ], "extra": [ 1, 184, 245, 169, 62, 107, 43, 76, 35, 72, 116, 3, 238, 47, 54, 36, 128, 69, 189, 206, 202, 51, 21, 213, 195, 31, 86, 18, 45, 86, 230, 69, 190, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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