Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adeca0e817e3eb7223935a10cec0d9f95b63ed56cd85d255464e6083bb54a648

Tx prefix hash: 4b8cb127bd589117d862090331d4740116d8f9edef8f8805f74c5f22e71ce45f
Tx public key: 9380381b5aa074f8c0910a73c6647061246f513f49bc97d6a5fbe4c55234610f
Timestamp: 1703856716 Timestamp [UCT]: 2023-12-29 13:31:56 Age [y:d:h:m:s]: 01:087:16:52:03
Block: 923718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323773 RingCT/type: yes/0
Extra: 019380381b5aa074f8c0910a73c6647061246f513f49bc97d6a5fbe4c55234610f021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47df192fb453c79d60aefbc74b0efffde8570ef0dc59a638871e3a184717b5b1 0.600000000000 1381454 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": 923728, "vin": [ { "gen": { "height": 923718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47df192fb453c79d60aefbc74b0efffde8570ef0dc59a638871e3a184717b5b1" } } ], "extra": [ 1, 147, 128, 56, 27, 90, 160, 116, 248, 192, 145, 10, 115, 198, 100, 112, 97, 36, 111, 81, 63, 73, 188, 151, 214, 165, 251, 228, 197, 82, 52, 97, 15, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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