Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfede944f71a0a7acc60528fd17939d2d73ed777cc13af1aa58799b8dc78251f

Tx prefix hash: 0a6bee46356d157d2f2b14807535e89bfc3b8984863685d0f820ab1efb42e88e
Tx public key: 8f8243d8b6d75de32627f7f690ab1ce929cedfe61484ab1e4b330e98390c0859
Timestamp: 1717550432 Timestamp [UCT]: 2024-06-05 01:20:32 Age [y:d:h:m:s]: 01:169:11:58:10
Block: 1037254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379711 RingCT/type: yes/0
Extra: 018f8243d8b6d75de32627f7f690ab1ce929cedfe61484ab1e4b330e98390c085902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f14daf9aa89d8a5fefd596d8faa1c232eff1fab63333131b0a9016e5df275d40 0.600000000000 1505785 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": 1037264, "vin": [ { "gen": { "height": 1037254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f14daf9aa89d8a5fefd596d8faa1c232eff1fab63333131b0a9016e5df275d40" } } ], "extra": [ 1, 143, 130, 67, 216, 182, 215, 93, 227, 38, 39, 247, 246, 144, 171, 28, 233, 41, 206, 223, 230, 20, 132, 171, 30, 75, 51, 14, 152, 57, 12, 8, 89, 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