Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2a333d2e711115f9898fa55c975b251b3f1c26ad0f5a38d49c00a2afaeb3927

Tx prefix hash: 551e3243f1f21eb78c6603a8169f5b191c0ca600503a20f875a723dab3cf9b9c
Tx public key: 0bc3bbd00af0dde5217b9bc823b5e4a7a7c73e1bbb8da10e93e1ed86a6971458
Timestamp: 1583641451 Timestamp [UCT]: 2020-03-08 04:24:11 Age [y:d:h:m:s]: 05:216:01:35:26
Block: 78709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1307268 RingCT/type: yes/0
Extra: 010bc3bbd00af0dde5217b9bc823b5e4a7a7c73e1bbb8da10e93e1ed86a69714580211000000166d997e00000000000000000000

1 output(s) for total of 336.670606364000 dcy

stealth address amount amount idx
00: c0ab237a1d48329dfb70dca0aa560b7314d3fc885e37ad2bea0f5962950235a3 336.670606364000 144179 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": 78719, "vin": [ { "gen": { "height": 78709 } } ], "vout": [ { "amount": 336670606364, "target": { "key": "c0ab237a1d48329dfb70dca0aa560b7314d3fc885e37ad2bea0f5962950235a3" } } ], "extra": [ 1, 11, 195, 187, 208, 10, 240, 221, 229, 33, 123, 155, 200, 35, 181, 228, 167, 167, 199, 62, 27, 187, 141, 161, 14, 147, 225, 237, 134, 166, 151, 20, 88, 2, 17, 0, 0, 0, 22, 109, 153, 126, 0, 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