Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d78bfc5ac2548780132ce799ba1f55e439458679ad2df2d385874931bcb23a1

Tx prefix hash: 53dcadedb7ef9eebf0c06ad43af8533d603ec8292559e96d31e84f9fd810411c
Tx public key: a4ea7d3fbbfb4f252f74e7295783e2d0405e0a6059ade4b5eafce09bd04506c8
Timestamp: 1721166406 Timestamp [UCT]: 2024-07-16 21:46:46 Age [y:d:h:m:s]: 00:246:21:27:22
Block: 1067241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176373 RingCT/type: yes/0
Extra: 01a4ea7d3fbbfb4f252f74e7295783e2d0405e0a6059ade4b5eafce09bd04506c8021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcd79eddb5292715fd5cef289f853c3345a162502afe8b469570dec50d6c0446 0.600000000000 1538000 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": 1067251, "vin": [ { "gen": { "height": 1067241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcd79eddb5292715fd5cef289f853c3345a162502afe8b469570dec50d6c0446" } } ], "extra": [ 1, 164, 234, 125, 63, 187, 251, 79, 37, 47, 116, 231, 41, 87, 131, 226, 208, 64, 94, 10, 96, 89, 173, 228, 181, 234, 252, 224, 155, 208, 69, 6, 200, 2, 17, 0, 0, 0, 7, 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