Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1f813b909f7a8a85fc6bf90caaffc4b3325519c7bfcd2c2e82aac1c3e169e6b

Tx prefix hash: 3b9e582d667cad3be07352804d4c96d51b733fe0c0e5b5990b9270dd4cb8d04b
Tx public key: 0ed1ffe747c630ff8958af34658ae8e372ff71d0bdf9d394b6f44c70e09ca46d
Timestamp: 1749955424 Timestamp [UCT]: 2025-06-15 02:43:44 Age [y:d:h:m:s]: 00:159:11:56:21
Block: 1305240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111772 RingCT/type: yes/0
Extra: 010ed1ffe747c630ff8958af34658ae8e372ff71d0bdf9d394b6f44c70e09ca46d02110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9858a779fa2df619ac9a7d358935904ae307644a770245a653e13d7b69cd389 0.600000000000 1792839 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": 1305250, "vin": [ { "gen": { "height": 1305240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9858a779fa2df619ac9a7d358935904ae307644a770245a653e13d7b69cd389" } } ], "extra": [ 1, 14, 209, 255, 231, 71, 198, 48, 255, 137, 88, 175, 52, 101, 138, 232, 227, 114, 255, 113, 208, 189, 249, 211, 148, 182, 244, 76, 112, 224, 156, 164, 109, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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