Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e687d55a838c323e80c6f8e55af8c2da2c72bc0c1706ef81f4fd09a8f797dcd4

Tx prefix hash: f9988debd4db6742cd8e47ce62c87281e01d8dbdef55962a0157ac0fed75e3d8
Tx public key: 25558a51da9c6231334b4c38f42ebcd8012b5255ea0c77ad5c2195af350b9f9d
Timestamp: 1730052339 Timestamp [UCT]: 2024-10-27 18:05:39 Age [y:d:h:m:s]: 00:160:18:53:44
Block: 1140854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114706 RingCT/type: yes/0
Extra: 0125558a51da9c6231334b4c38f42ebcd8012b5255ea0c77ad5c2195af350b9f9d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a201b371796eb2056568b3d2aa2f9a0b9c6dba38a56363b92aed99a569511086 0.600000000000 1624657 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": 1140864, "vin": [ { "gen": { "height": 1140854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a201b371796eb2056568b3d2aa2f9a0b9c6dba38a56363b92aed99a569511086" } } ], "extra": [ 1, 37, 85, 138, 81, 218, 156, 98, 49, 51, 75, 76, 56, 244, 46, 188, 216, 1, 43, 82, 85, 234, 12, 119, 173, 92, 33, 149, 175, 53, 11, 159, 157, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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