Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0be76eb6eca663e2198b4db702fc01df8956d8fdfd5ae2b27ae837349debc23f

Tx prefix hash: 66953b14f84b2f64e446750f4d6dc4b3b00c2568d66680d339d0ecdd38454dab
Tx public key: 4b601e024bc2a3b44bd1e73313f4198a959d28239fbe25462b9e8184804ab78d
Timestamp: 1637334149 Timestamp [UCT]: 2021-11-19 15:02:29 Age [y:d:h:m:s]: 03:180:17:44:38
Block: 377676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 907815 RingCT/type: yes/0
Extra: 014b601e024bc2a3b44bd1e73313f4198a959d28239fbe25462b9e8184804ab78d02110000000806faf294000000000000000000

1 output(s) for total of 34.404510744000 dcy

stealth address amount amount idx
00: 40d3906de39f288d58bc166f7bc4d900fbc4013a7e727bf31f4a48311f680746 34.404510744000 763879 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": 377686, "vin": [ { "gen": { "height": 377676 } } ], "vout": [ { "amount": 34404510744, "target": { "key": "40d3906de39f288d58bc166f7bc4d900fbc4013a7e727bf31f4a48311f680746" } } ], "extra": [ 1, 75, 96, 30, 2, 75, 194, 163, 180, 75, 209, 231, 51, 19, 244, 25, 138, 149, 157, 40, 35, 159, 190, 37, 70, 43, 158, 129, 132, 128, 74, 183, 141, 2, 17, 0, 0, 0, 8, 6, 250, 242, 148, 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