Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81b18e6c6ed1476f0805d651bab0ad37fc817e897e9de87f6913992811cd24ca

Tx prefix hash: 0d39d8568bdf9cef5e13848b6d54d169bfc0546e462fb8481488c2ca63b652cb
Tx public key: a314b7805ce68ee994b97f1af526e0b4fb19f765394f6a60a341053034cb5475
Timestamp: 1681574239 Timestamp [UCT]: 2023-04-15 15:57:19 Age [y:d:h:m:s]: 02:207:16:00:21
Block: 739222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 668293 RingCT/type: yes/0
Extra: 01a314b7805ce68ee994b97f1af526e0b4fb19f765394f6a60a341053034cb5475021100000001b3164c24000000000000000000

1 output(s) for total of 2.180975903000 dcy

stealth address amount amount idx
00: aac88f41c1f2b18592fc0e4dbbe2ae349eb66ad1e7df56a4f6647794aec28f7d 2.180975903000 1186059 of 0

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": 739232, "vin": [ { "gen": { "height": 739222 } } ], "vout": [ { "amount": 2180975903, "target": { "key": "aac88f41c1f2b18592fc0e4dbbe2ae349eb66ad1e7df56a4f6647794aec28f7d" } } ], "extra": [ 1, 163, 20, 183, 128, 92, 230, 142, 233, 148, 185, 127, 26, 245, 38, 224, 180, 251, 25, 247, 101, 57, 79, 106, 96, 163, 65, 5, 48, 52, 203, 84, 117, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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