Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f2cff2c39926a8998e17e93f30183c0716e85ac4ee20f8fe217c187f4ae75c8

Tx prefix hash: 968560e1068c037712fcd922db8cef333a93c80c5de894f23bf4171fe3dbe613
Tx public key: 2d1c7abd70aa3882f8acef28033767f1a83b905d3c967dc41362d994065049fa
Timestamp: 1721985631 Timestamp [UCT]: 2024-07-26 09:20:31 Age [y:d:h:m:s]: 00:249:10:17:52
Block: 1074016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178170 RingCT/type: yes/0
Extra: 012d1c7abd70aa3882f8acef28033767f1a83b905d3c967dc41362d994065049fa021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5c99fbf26bd959ab9cca3bd5ef7e1e8c7cf335abbeced59f46829398c5fde03 0.600000000000 1546525 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": 1074026, "vin": [ { "gen": { "height": 1074016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5c99fbf26bd959ab9cca3bd5ef7e1e8c7cf335abbeced59f46829398c5fde03" } } ], "extra": [ 1, 45, 28, 122, 189, 112, 170, 56, 130, 248, 172, 239, 40, 3, 55, 103, 241, 168, 59, 144, 93, 60, 150, 125, 196, 19, 98, 217, 148, 6, 80, 73, 250, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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