Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edde6f8ba31b97036dab39a3508a5a77b89d00c9d5a5101af4c01a35acc3da2a

Tx prefix hash: 5366dd0f2603d94f3ee7bda14146e867695ffa2572403197da53ee8646f97bb2
Tx public key: 2cad1ea13548a3b216b095ee21459310090e575e44f102c7d027270a50d818d2
Timestamp: 1578826491 Timestamp [UCT]: 2020-01-12 10:54:51 Age [y:d:h:m:s]: 05:293:19:59:33
Block: 43887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1357877 RingCT/type: yes/0
Extra: 012cad1ea13548a3b216b095ee21459310090e575e44f102c7d027270a50d818d20211000000324943cd9f000000000000000000

1 output(s) for total of 439.121794528000 dcy

stealth address amount amount idx
00: 03e3131a88f68fcce158b8d836e47feea1954323bf3f60f9d9a59856f9d5e3d8 439.121794528000 79654 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": 43897, "vin": [ { "gen": { "height": 43887 } } ], "vout": [ { "amount": 439121794528, "target": { "key": "03e3131a88f68fcce158b8d836e47feea1954323bf3f60f9d9a59856f9d5e3d8" } } ], "extra": [ 1, 44, 173, 30, 161, 53, 72, 163, 178, 22, 176, 149, 238, 33, 69, 147, 16, 9, 14, 87, 94, 68, 241, 2, 199, 208, 39, 39, 10, 80, 216, 24, 210, 2, 17, 0, 0, 0, 50, 73, 67, 205, 159, 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