Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15f11e7bd4436f8ad19077e67eacb0afe1fae1b1ce5759e0bbadd0cdf3d264e2

Tx prefix hash: 0f9a419273cc8e630f29daefbdb3b432554731ac6b42e9bc9f0351fe56826cce
Tx public key: fc172b1e4f36f34d68af5c7ef59fc683870dcc53104b3cee5339c2ee065fee4f
Timestamp: 1706319147 Timestamp [UCT]: 2024-01-27 01:32:27 Age [y:d:h:m:s]: 01:030:03:03:45
Block: 944106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282588 RingCT/type: yes/0
Extra: 01fc172b1e4f36f34d68af5c7ef59fc683870dcc53104b3cee5339c2ee065fee4f02110000000710a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7a10dc619bbfa73ab424bdd9a55f59260f4fc290a69e3425b00446d056ab729 0.600000000000 1402332 of 15

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": 944116, "vin": [ { "gen": { "height": 944106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7a10dc619bbfa73ab424bdd9a55f59260f4fc290a69e3425b00446d056ab729" } } ], "extra": [ 1, 252, 23, 43, 30, 79, 54, 243, 77, 104, 175, 92, 126, 245, 159, 198, 131, 135, 13, 204, 83, 16, 75, 60, 238, 83, 57, 194, 238, 6, 95, 238, 79, 2, 17, 0, 0, 0, 7, 16, 161, 116, 143, 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