Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e701af5555d62353cefdfa84d5a599017d1bd6f9121af09edf5fe0edd78d67a

Tx prefix hash: 357ef89ab2cfb64a5b50d040e40b0dd0085979a87c702f5598f8ceeb780c45a0
Tx public key: da21f06345a5ee53e3a62ee5b4c95e1e4f6b060f8bf2710a70facaa818969b57
Timestamp: 1732587068 Timestamp [UCT]: 2024-11-26 02:11:08 Age [y:d:h:m:s]: 00:167:01:35:12
Block: 1161812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119230 RingCT/type: yes/0
Extra: 01da21f06345a5ee53e3a62ee5b4c95e1e4f6b060f8bf2710a70facaa818969b570211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8c824693bf62e3c50c8c5ce8b6dff43517b13a29ffa379eaaf446f8466b8e0c 0.600000000000 1647467 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": 1161822, "vin": [ { "gen": { "height": 1161812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8c824693bf62e3c50c8c5ce8b6dff43517b13a29ffa379eaaf446f8466b8e0c" } } ], "extra": [ 1, 218, 33, 240, 99, 69, 165, 238, 83, 227, 166, 46, 229, 180, 201, 94, 30, 79, 107, 6, 15, 139, 242, 113, 10, 112, 250, 202, 168, 24, 150, 155, 87, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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