Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 830e72a229da5f9d67d719bc3bebe11fc2aa36b6321f9a26e9d705ba25cafff8

Tx prefix hash: 8593e3e3688a5d19e7730b35cbc270d9766a8b245d95286f31db868a461f65e3
Tx public key: d23d777326bdf5d950135c27e309180a98c48ccf17dff483f83d50bf2730a576
Timestamp: 1695837660 Timestamp [UCT]: 2023-09-27 18:01:00 Age [y:d:h:m:s]: 01:049:16:33:09
Block: 857441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296747 RingCT/type: yes/0
Extra: 01d23d777326bdf5d950135c27e309180a98c48ccf17dff483f83d50bf2730a57602110000000f4b8f5122000000000000000000

1 output(s) for total of 0.894747557000 dcy

stealth address amount amount idx
00: 264e3c55778e42868d6934ed91616c2f09909d00d639a979fbb3d36b72475fe7 0.894747557000 1311567 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": 857451, "vin": [ { "gen": { "height": 857441 } } ], "vout": [ { "amount": 894747557, "target": { "key": "264e3c55778e42868d6934ed91616c2f09909d00d639a979fbb3d36b72475fe7" } } ], "extra": [ 1, 210, 61, 119, 115, 38, 189, 245, 217, 80, 19, 92, 39, 227, 9, 24, 10, 152, 196, 140, 207, 23, 223, 244, 131, 248, 61, 80, 191, 39, 48, 165, 118, 2, 17, 0, 0, 0, 15, 75, 143, 81, 34, 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