Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6488f2744e5b3017e3d2e974ae50ee453846b537d24ee2b9ff918696a8138d98

Tx prefix hash: 3883cba411428efd41d7a546bceb772504ede2df718960e22dbe09aaa95b9c1e
Tx public key: 145fe84bbd5bc22115c8b6d11562a088c2e1f3f3c6166b8d01eb9316338f099d
Timestamp: 1710350367 Timestamp [UCT]: 2024-03-13 17:19:27 Age [y:d:h:m:s]: 01:241:21:59:22
Block: 977573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431596 RingCT/type: yes/0
Extra: 01145fe84bbd5bc22115c8b6d11562a088c2e1f3f3c6166b8d01eb9316338f099d02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 603b87841b2bbe621ab6cf7736cd24d6794cf7499132e71409d591c03af9f0b5 0.600000000000 1437576 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": 977583, "vin": [ { "gen": { "height": 977573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "603b87841b2bbe621ab6cf7736cd24d6794cf7499132e71409d591c03af9f0b5" } } ], "extra": [ 1, 20, 95, 232, 75, 189, 91, 194, 33, 21, 200, 182, 209, 21, 98, 160, 136, 194, 225, 243, 243, 198, 22, 107, 141, 1, 235, 147, 22, 51, 143, 9, 157, 2, 17, 0, 0, 0, 9, 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