Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b415f1f88afd37203b28c0d9a37b34cc3d74a3c6e6774cb6ee0a50425ec96787

Tx prefix hash: 1c665c125f5a9097a7958e4b8a4f809d11b209a6987f9e1a7161cb8bac77a2f1
Tx public key: 52087281c1cf85bad2ff779f1a10a1f8c8ea7aa1c05e4f3821e3e5fef04ea93c
Timestamp: 1738651823 Timestamp [UCT]: 2025-02-04 06:50:23 Age [y:d:h:m:s]: 00:290:14:25:30
Block: 1211752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205462 RingCT/type: yes/0
Extra: 0152087281c1cf85bad2ff779f1a10a1f8c8ea7aa1c05e4f3821e3e5fef04ea93c0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d2f465d4c7b655b21ab50764e15fa48b9f89bffa7605c75de9a8a18d173db25 0.600000000000 1698515 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": 1211762, "vin": [ { "gen": { "height": 1211752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d2f465d4c7b655b21ab50764e15fa48b9f89bffa7605c75de9a8a18d173db25" } } ], "extra": [ 1, 82, 8, 114, 129, 193, 207, 133, 186, 210, 255, 119, 159, 26, 16, 161, 248, 200, 234, 122, 161, 192, 94, 79, 56, 33, 227, 229, 254, 240, 78, 169, 60, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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