Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f49526a6f557d1289c9720181ae977017f311d4d948a0bbf6ccf6320ddf4b504

Tx prefix hash: 90b7202f7a94cc83fbb219d0aafc2f9cf9d0c2ae77d5b5c5816db024aa9e98eb
Tx public key: 875ac1156b70d6d5a49381e794c275b19fa7d199598fbaf1ea3f7454301f0467
Timestamp: 1699204033 Timestamp [UCT]: 2023-11-05 17:07:13 Age [y:d:h:m:s]: 02:028:09:53:25
Block: 885148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 540122 RingCT/type: yes/0
Extra: 01875ac1156b70d6d5a49381e794c275b19fa7d199598fbaf1ea3f7454301f046702110000000175e3f0e9000000000000000000

1 output(s) for total of 0.716369750000 dcy

stealth address amount amount idx
00: ecb0f11449aeff1d3588d6bddeaa63bd3174ebc2e9633c37ae1a805f20bc3e7a 0.716369750000 1340903 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": 885158, "vin": [ { "gen": { "height": 885148 } } ], "vout": [ { "amount": 716369750, "target": { "key": "ecb0f11449aeff1d3588d6bddeaa63bd3174ebc2e9633c37ae1a805f20bc3e7a" } } ], "extra": [ 1, 135, 90, 193, 21, 107, 112, 214, 213, 164, 147, 129, 231, 148, 194, 117, 177, 159, 167, 209, 153, 89, 143, 186, 241, 234, 63, 116, 84, 48, 31, 4, 103, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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