Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d92abd340ebeb89e5c2ac386b91ef543c98418330c56495cc8d5d0d4d08dbc9

Tx prefix hash: 36400e71ae6734f8cc4e54e5a423d76197cf41cc87bd290ef7d056e3fdeda5fd
Tx public key: 6a3a2a3646eca878deb452059d1bee53d21f35cb9980e7a8acf849d84f083f82
Timestamp: 1735752729 Timestamp [UCT]: 2025-01-01 17:32:09 Age [y:d:h:m:s]: 00:167:00:24:56
Block: 1188020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119089 RingCT/type: yes/0
Extra: 016a3a2a3646eca878deb452059d1bee53d21f35cb9980e7a8acf849d84f083f8202110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f68316850c5879e05c304b4e07788f172f95c20f9a8897e24057a4d8ada313a5 0.600000000000 1674519 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": 1188030, "vin": [ { "gen": { "height": 1188020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f68316850c5879e05c304b4e07788f172f95c20f9a8897e24057a4d8ada313a5" } } ], "extra": [ 1, 106, 58, 42, 54, 70, 236, 168, 120, 222, 180, 82, 5, 157, 27, 238, 83, 210, 31, 53, 203, 153, 128, 231, 168, 172, 248, 73, 216, 79, 8, 63, 130, 2, 17, 0, 0, 0, 10, 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