Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f53bac45316c880ee342c72138f6491e423af1df1826c4a8da588738a343914

Tx prefix hash: bd0702b7ada3f0395141a174f47e1de2b2062db41ff4bd6be28f8a2b66981a29
Tx public key: 5b95b7ac9682d8fc5d6d2b53d4394ff1e675f3c3c406d5bb2905b92c3a490520
Timestamp: 1589363460 Timestamp [UCT]: 2020-05-13 09:51:00 Age [y:d:h:m:s]: 04:292:01:36:34
Block: 100461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128587 RingCT/type: yes/0
Extra: 015b95b7ac9682d8fc5d6d2b53d4394ff1e675f3c3c406d5bb2905b92c3a4905200211000004e6a86a1a65000000000000000000

1 output(s) for total of 285.188339729000 dcy

stealth address amount amount idx
00: 9c8b7cedaadaf77f21f9b0f13493bca3c06dc588f18a1b856b0f8e05470dcf2b 285.188339729000 177001 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": 100471, "vin": [ { "gen": { "height": 100461 } } ], "vout": [ { "amount": 285188339729, "target": { "key": "9c8b7cedaadaf77f21f9b0f13493bca3c06dc588f18a1b856b0f8e05470dcf2b" } } ], "extra": [ 1, 91, 149, 183, 172, 150, 130, 216, 252, 93, 109, 43, 83, 212, 57, 79, 241, 230, 117, 243, 195, 196, 6, 213, 187, 41, 5, 185, 44, 58, 73, 5, 32, 2, 17, 0, 0, 4, 230, 168, 106, 26, 101, 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