Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe84c7a575fab71dd496d95bbee6a36d973f5194355649617670d98e4e62f9d1

Tx prefix hash: 708d070efbec5e1779fce35c5115e099a61b41a8bc38936d5c40af60ef98c1c4
Tx public key: 1ebb2bcc4bcfd42560b1641d89c3767d3b95a9b3512cf11fd3b3b85ffd553bb9
Timestamp: 1707010506 Timestamp [UCT]: 2024-02-04 01:35:06 Age [y:d:h:m:s]: 01:070:23:03:07
Block: 949844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311787 RingCT/type: yes/0
Extra: 011ebb2bcc4bcfd42560b1641d89c3767d3b95a9b3512cf11fd3b3b85ffd553bb902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9088bcb99f0b3aedef5b1e99464b5e4be6d2b10cb405e69402b4516208925e2d 0.600000000000 1408376 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": 949854, "vin": [ { "gen": { "height": 949844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9088bcb99f0b3aedef5b1e99464b5e4be6d2b10cb405e69402b4516208925e2d" } } ], "extra": [ 1, 30, 187, 43, 204, 75, 207, 212, 37, 96, 177, 100, 29, 137, 195, 118, 125, 59, 149, 169, 179, 81, 44, 241, 31, 211, 179, 184, 95, 253, 85, 59, 185, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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