Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7516275d5ce5ddbec3cc47a908b8b70f02a2b2389a8521077357cbf8b26d8bda

Tx prefix hash: 5ee2eec7ab5af5d5d4d3f9032c53049b5d96318d264e695dec17c2ea266fe0cb
Tx public key: fe735bb075e74d4d23270a850701da660c9eafbc57a1814fa01c09ea0029cda2
Timestamp: 1632101528 Timestamp [UCT]: 2021-09-20 01:32:08 Age [y:d:h:m:s]: 03:142:14:19:57
Block: 337233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 877655 RingCT/type: yes/0
Extra: 01fe735bb075e74d4d23270a850701da660c9eafbc57a1814fa01c09ea0029cda202110000000f8d0de867000000000000000000

1 output(s) for total of 46.838989289000 dcy

stealth address amount amount idx
00: e32e6223b8a2cfec6b49cd2896f4f4004ed2bd0b9c24f009fe1d5866ae810033 46.838989289000 694486 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": 337243, "vin": [ { "gen": { "height": 337233 } } ], "vout": [ { "amount": 46838989289, "target": { "key": "e32e6223b8a2cfec6b49cd2896f4f4004ed2bd0b9c24f009fe1d5866ae810033" } } ], "extra": [ 1, 254, 115, 91, 176, 117, 231, 77, 77, 35, 39, 10, 133, 7, 1, 218, 102, 12, 158, 175, 188, 87, 161, 129, 79, 160, 28, 9, 234, 0, 41, 205, 162, 2, 17, 0, 0, 0, 15, 141, 13, 232, 103, 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