Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf69c323e3a04c103b1c8d8094e53bcae87c03ba26db62dea9b0c4e501a9f215

Tx prefix hash: ae00f57d9efb23d59de9b81442ebc3ab87388fed9d7f585a61a145da60cae20a
Tx public key: 8912fbf318260b8dbe7fd42d0327ec4dfe30e448899bb8aeed1cfde5de83522a
Timestamp: 1725830672 Timestamp [UCT]: 2024-09-08 21:24:32 Age [y:d:h:m:s]: 00:080:12:54:32
Block: 1105900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57585 RingCT/type: yes/0
Extra: 018912fbf318260b8dbe7fd42d0327ec4dfe30e448899bb8aeed1cfde5de83522a02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 819e6fa9b4d3e0f243761b47a6cabc91e00a6a56598188f1d887d4cf48716f00 0.600000000000 1583399 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": 1105910, "vin": [ { "gen": { "height": 1105900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "819e6fa9b4d3e0f243761b47a6cabc91e00a6a56598188f1d887d4cf48716f00" } } ], "extra": [ 1, 137, 18, 251, 243, 24, 38, 11, 141, 190, 127, 212, 45, 3, 39, 236, 77, 254, 48, 228, 72, 137, 155, 184, 174, 237, 28, 253, 229, 222, 131, 82, 42, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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