Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3243cf5a01e4de16ee3cb8a27b2651627bdd74879413e4f1adbb3d5c7b75d115

Tx prefix hash: f48ccbc2a5219dcc1026e3030535e6769793cbf6b18d7dd885d5223784a1e327
Tx public key: 678bc851eeb83c40917609015fd1334ec6a7f99c6b942ca16915fd436cb69ace
Timestamp: 1696804065 Timestamp [UCT]: 2023-10-08 22:27:45 Age [y:d:h:m:s]: 01:038:03:17:23
Block: 865454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288464 RingCT/type: yes/0
Extra: 01678bc851eeb83c40917609015fd1334ec6a7f99c6b942ca16915fd436cb69ace021100000001faf35c9c000000000000000000

1 output(s) for total of 0.832514229000 dcy

stealth address amount amount idx
00: db49290edbcd61198a4a230ee4700f2cd2f6ec7975f65d76bfe02d2415b0a1a3 0.832514229000 1319990 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": 865464, "vin": [ { "gen": { "height": 865454 } } ], "vout": [ { "amount": 832514229, "target": { "key": "db49290edbcd61198a4a230ee4700f2cd2f6ec7975f65d76bfe02d2415b0a1a3" } } ], "extra": [ 1, 103, 139, 200, 81, 238, 184, 60, 64, 145, 118, 9, 1, 95, 209, 51, 78, 198, 167, 249, 156, 107, 148, 44, 161, 105, 21, 253, 67, 108, 182, 154, 206, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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