Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d3a2f885052f2f1d8157f56d57e3b4a8c3087717d78dc037b0c98c6da9869c1

Tx prefix hash: c9daa2214a2671a229c52f92da52738e43b8c479c36152b7ebceae2e2faa36d5
Tx public key: b2d664f2cea14f5ca4ec80f1bd66039fdf0d2a32129d76a45b029ac54e57f8c4
Timestamp: 1719039283 Timestamp [UCT]: 2024-06-22 06:54:43 Age [y:d:h:m:s]: 00:245:20:53:39
Block: 1049578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175661 RingCT/type: yes/0
Extra: 01b2d664f2cea14f5ca4ec80f1bd66039fdf0d2a32129d76a45b029ac54e57f8c40211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f70efe99ad0d12fb4da997e15dd42a5fc0c3a876a1e434892d1e68b5af265ec 0.600000000000 1519677 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": 1049588, "vin": [ { "gen": { "height": 1049578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f70efe99ad0d12fb4da997e15dd42a5fc0c3a876a1e434892d1e68b5af265ec" } } ], "extra": [ 1, 178, 214, 100, 242, 206, 161, 79, 92, 164, 236, 128, 241, 189, 102, 3, 159, 223, 13, 42, 50, 18, 157, 118, 164, 91, 2, 154, 197, 78, 87, 248, 196, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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