Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88ef028939cc98d27cf934d7be01a3ee33d0af63f4b509852145c8d413dc294c

Tx prefix hash: 0407c139e76dde8dc96ff0cd0130c6c65bb0b751c2ae0567920f102516b398be
Tx public key: 2fb499edab2c8e85c97f24a7c28cd95644262848dc99538c2a0b439df7889f65
Timestamp: 1727091954 Timestamp [UCT]: 2024-09-23 11:45:54 Age [y:d:h:m:s]: 00:062:07:21:26
Block: 1116353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44529 RingCT/type: yes/0
Extra: 012fb499edab2c8e85c97f24a7c28cd95644262848dc99538c2a0b439df7889f65021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f41c576bca285e21f6f197e36ca976a279aa553e1288dba7f3597a29370ff903 0.600000000000 1596804 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": 1116363, "vin": [ { "gen": { "height": 1116353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f41c576bca285e21f6f197e36ca976a279aa553e1288dba7f3597a29370ff903" } } ], "extra": [ 1, 47, 180, 153, 237, 171, 44, 142, 133, 201, 127, 36, 167, 194, 140, 217, 86, 68, 38, 40, 72, 220, 153, 83, 140, 42, 11, 67, 157, 247, 136, 159, 101, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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