Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa4b97f553c1160ebed447968e40df31f9de2b4c7d556b73f4baafb63ffe9d32

Tx prefix hash: f160743a44055d4c55a5ff993fbc317eef1394fc275915e985a9aa9e8726aacd
Tx public key: 264f1a0d0c1c7a8fcd13ce2ee26b9019e5f48b9446be3796f77be1cb19b39db2
Timestamp: 1736574363 Timestamp [UCT]: 2025-01-11 05:46:03 Age [y:d:h:m:s]: 00:113:06:36:43
Block: 1194827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80752 RingCT/type: yes/0
Extra: 01264f1a0d0c1c7a8fcd13ce2ee26b9019e5f48b9446be3796f77be1cb19b39db2021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b94fb568ba98a97c3a0280e31bfb82ea1167e97b30fa8aa91fee6ac538a8e4a0 0.600000000000 1681404 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": 1194837, "vin": [ { "gen": { "height": 1194827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b94fb568ba98a97c3a0280e31bfb82ea1167e97b30fa8aa91fee6ac538a8e4a0" } } ], "extra": [ 1, 38, 79, 26, 13, 12, 28, 122, 143, 205, 19, 206, 46, 226, 107, 144, 25, 229, 244, 139, 148, 70, 190, 55, 150, 247, 123, 225, 203, 25, 179, 157, 178, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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