Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14ceb74802319cd15197046fc2192e9d4ab1ae4f174d73df9664a45c9b47d412

Tx prefix hash: 95e4c5b629ca8aba3ad954f8e97ef5e6fc1676e78d1d410057ae156ba588da1d
Tx public key: f2953817a7104e8ad850a19daf3b0c682dfeb334f5248dcdc6dc55a0024cc7ee
Timestamp: 1709844719 Timestamp [UCT]: 2024-03-07 20:51:59 Age [y:d:h:m:s]: 01:011:17:48:56
Block: 973369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269393 RingCT/type: yes/0
Extra: 01f2953817a7104e8ad850a19daf3b0c682dfeb334f5248dcdc6dc55a0024cc7ee02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 574bb8389a731e50d843d10b53af731a706c43d5b6ed1bd69556b558144e34f7 0.600000000000 1433304 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": 973379, "vin": [ { "gen": { "height": 973369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "574bb8389a731e50d843d10b53af731a706c43d5b6ed1bd69556b558144e34f7" } } ], "extra": [ 1, 242, 149, 56, 23, 167, 16, 78, 138, 216, 80, 161, 157, 175, 59, 12, 104, 45, 254, 179, 52, 245, 36, 141, 205, 198, 220, 85, 160, 2, 76, 199, 238, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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