Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f682cecb5645455aa3da2bd3692b454d7a0d58bed11ad6bdd6982e0282f8cdb

Tx prefix hash: 89c7a061e94a66438eb4f01e9649d5e96cbd5d9895d47a147d53d6ce0ea97cca
Tx public key: a8188f2fb262ba0f56c9f65c7851899a10a27492831e93fbc2e85a4ac69e0dec
Timestamp: 1737544518 Timestamp [UCT]: 2025-01-22 11:15:18 Age [y:d:h:m:s]: 00:146:15:04:36
Block: 1202812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104543 RingCT/type: yes/0
Extra: 01a8188f2fb262ba0f56c9f65c7851899a10a27492831e93fbc2e85a4ac69e0dec021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 810d1f671f0b1606181781b19b2f1206ff2bfead24e9daf387477884de9f7925 0.600000000000 1689479 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": 1202822, "vin": [ { "gen": { "height": 1202812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "810d1f671f0b1606181781b19b2f1206ff2bfead24e9daf387477884de9f7925" } } ], "extra": [ 1, 168, 24, 143, 47, 178, 98, 186, 15, 86, 201, 246, 92, 120, 81, 137, 154, 16, 162, 116, 146, 131, 30, 147, 251, 194, 232, 90, 74, 198, 158, 13, 236, 2, 17, 0, 0, 0, 8, 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