Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4d0e2c779e16ca452cfa71b7d8777d863396611aa1a367bf45168d5ab43fa5e

Tx prefix hash: 8f0502add5181d998ff672c748d8f0432ed70384a2e73f406eeea56e2965dd92
Tx public key: d7d1ac31d58cde5dd08daf49cd9f56f4864226261d9bca1d59c72657ebd6ed98
Timestamp: 1711257977 Timestamp [UCT]: 2024-03-24 05:26:17 Age [y:d:h:m:s]: 01:229:20:03:50
Block: 985098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422931 RingCT/type: yes/0
Extra: 01d7d1ac31d58cde5dd08daf49cd9f56f4864226261d9bca1d59c72657ebd6ed9802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9e11c4b0c5a8f4f8cbc3da5b64bce1e45faf83e15cd6954e930cb3560774276 0.600000000000 1445305 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": 985108, "vin": [ { "gen": { "height": 985098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9e11c4b0c5a8f4f8cbc3da5b64bce1e45faf83e15cd6954e930cb3560774276" } } ], "extra": [ 1, 215, 209, 172, 49, 213, 140, 222, 93, 208, 141, 175, 73, 205, 159, 86, 244, 134, 66, 38, 38, 29, 155, 202, 29, 89, 199, 38, 87, 235, 214, 237, 152, 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