Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2480346fb0369e312e310502ab373d7f7067731dfdbfd98c3635ae8904388c09

Tx prefix hash: a46bec4a4932d74ca320b2b3107128c861fe6dbfd0a6744ec4f69c8fafea6319
Tx public key: 642b76cf8e4e42af7ba98ae9a2142881d9b92cbcef1cfdfb04f0938b681a107b
Timestamp: 1705062092 Timestamp [UCT]: 2024-01-12 12:21:32 Age [y:d:h:m:s]: 00:307:14:00:20
Block: 933699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220231 RingCT/type: yes/0
Extra: 01642b76cf8e4e42af7ba98ae9a2142881d9b92cbcef1cfdfb04f0938b681a107b02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f86f620fbf35774a46e2f7b415a95a9ce782be41a1b981e230c3c89fa95f06b6 0.600000000000 1391669 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": 933709, "vin": [ { "gen": { "height": 933699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f86f620fbf35774a46e2f7b415a95a9ce782be41a1b981e230c3c89fa95f06b6" } } ], "extra": [ 1, 100, 43, 118, 207, 142, 78, 66, 175, 123, 169, 138, 233, 162, 20, 40, 129, 217, 185, 44, 188, 239, 28, 253, 251, 4, 240, 147, 139, 104, 26, 16, 123, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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