Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 347672a89016f00610d33f99bd116d74069941da3ab0df2ecdcae9f887d29edf

Tx prefix hash: 441d4bbb1be17f5abdf7f3a6fc1bc53369951278a69e962d040f3895f623571f
Tx public key: 5a4dc875cf5361ea1a5e9055d5df38138e10a2c0db807bc35062d10babeae2e4
Timestamp: 1697337672 Timestamp [UCT]: 2023-10-15 02:41:12 Age [y:d:h:m:s]: 01:109:10:05:26
Block: 869874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339202 RingCT/type: yes/0
Extra: 015a4dc875cf5361ea1a5e9055d5df38138e10a2c0db807bc35062d10babeae2e40211000000014b8f5122000000000000000000

1 output(s) for total of 0.804908222000 dcy

stealth address amount amount idx
00: 8a103339d601f2ad5fe54225b88fb53b8b80e17f8138c26caefb22d3891c8988 0.804908222000 1324739 of 0

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": 869884, "vin": [ { "gen": { "height": 869874 } } ], "vout": [ { "amount": 804908222, "target": { "key": "8a103339d601f2ad5fe54225b88fb53b8b80e17f8138c26caefb22d3891c8988" } } ], "extra": [ 1, 90, 77, 200, 117, 207, 83, 97, 234, 26, 94, 144, 85, 213, 223, 56, 19, 142, 16, 162, 192, 219, 128, 123, 195, 80, 98, 209, 11, 171, 234, 226, 228, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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