Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5f1e3d45106a77ffd1aef75508beab74cc8ad47aa6a42ae50e552508545544e

Tx prefix hash: 891034bb11cb16d53a9b4dcfe643f836b111ab82c232dd4292bbcad5f7f69b72
Tx public key: 20c9a89c96d2af0cbf3d8e33885718e8664e2ab01a9d0c4b55dbc72a71390d46
Timestamp: 1745293608 Timestamp [UCT]: 2025-04-22 03:46:48 Age [y:d:h:m:s]: 00:022:16:44:24
Block: 1266736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16248 RingCT/type: yes/0
Extra: 0120c9a89c96d2af0cbf3d8e33885718e8664e2ab01a9d0c4b55dbc72a71390d46021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89697343151a6d4b31d693256e21bd1ffe8299a9fe763a571ee75d20ccad8f27 0.600000000000 1753957 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": 1266746, "vin": [ { "gen": { "height": 1266736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89697343151a6d4b31d693256e21bd1ffe8299a9fe763a571ee75d20ccad8f27" } } ], "extra": [ 1, 32, 201, 168, 156, 150, 210, 175, 12, 191, 61, 142, 51, 136, 87, 24, 232, 102, 78, 42, 176, 26, 157, 12, 75, 85, 219, 199, 42, 113, 57, 13, 70, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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