Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a085cd77e8fa1831be649d9a3a36db568ccf30bc6072cca513cb6b74db7a72a

Tx prefix hash: 45218947c004b1fe3f02a3d54270ee4bb924f04315878dca6341b05aa4a24eec
Tx public key: ae7b3f26289607f7ef18f96df9ce7f2557451ddd21fc00fe00f23de8e78f926e
Timestamp: 1633194414 Timestamp [UCT]: 2021-10-02 17:06:54 Age [y:d:h:m:s]: 03:224:09:28:19
Block: 345321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 937120 RingCT/type: yes/0
Extra: 01ae7b3f26289607f7ef18f96df9ce7f2557451ddd21fc00fe00f23de8e78f926e0211000000023fc41461000000000000000000

1 output(s) for total of 44.036075457000 dcy

stealth address amount amount idx
00: ce433d9d71751389d8bbe950f1d081f5a36207d5a2896db0955ee062c3cd91c2 44.036075457000 708431 of 0

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": 345331, "vin": [ { "gen": { "height": 345321 } } ], "vout": [ { "amount": 44036075457, "target": { "key": "ce433d9d71751389d8bbe950f1d081f5a36207d5a2896db0955ee062c3cd91c2" } } ], "extra": [ 1, 174, 123, 63, 38, 40, 150, 7, 247, 239, 24, 249, 109, 249, 206, 127, 37, 87, 69, 29, 221, 33, 252, 0, 254, 0, 242, 61, 232, 231, 143, 146, 110, 2, 17, 0, 0, 0, 2, 63, 196, 20, 97, 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