Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1f5575a3fb95eea6a7280984db28256658a9b5bb8512eaef1acb429d5620586

Tx prefix hash: 6944f0e413ac9a9067ec5071a6cfca3ecc005b728ad7d44073337271345d961e
Tx public key: 69021dc8aa79a44281f1d1f6686beacfcda2a3e726ab54291628d3c37ad07a94
Timestamp: 1706149744 Timestamp [UCT]: 2024-01-25 02:29:04 Age [y:d:h:m:s]: 00:267:08:59:43
Block: 942704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191553 RingCT/type: yes/0
Extra: 0169021dc8aa79a44281f1d1f6686beacfcda2a3e726ab54291628d3c37ad07a9402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90f19d62aa9b07d8c732687d096d41e3cd1d3fee21362fc18f12dd8b2451e4af 0.600000000000 1400880 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": 942714, "vin": [ { "gen": { "height": 942704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90f19d62aa9b07d8c732687d096d41e3cd1d3fee21362fc18f12dd8b2451e4af" } } ], "extra": [ 1, 105, 2, 29, 200, 170, 121, 164, 66, 129, 241, 209, 246, 104, 107, 234, 207, 205, 162, 163, 231, 38, 171, 84, 41, 22, 40, 211, 195, 122, 208, 122, 148, 2, 17, 0, 0, 0, 4, 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