Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5377e7e94fe03b66a197814fb04a09ec06efe611fdd942c0cf586acf58ce7f7c

Tx prefix hash: 8e8b238581db705228d63b8fe24aecba8c38dca7f1a3f1317569829755289b77
Tx public key: 904ef3609e63f41e9293538613272fb3e29b09a441ab7e8b705d92c4cd56a25f
Timestamp: 1702798630 Timestamp [UCT]: 2023-12-17 07:37:10 Age [y:d:h:m:s]: 01:109:21:16:13
Block: 914951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339654 RingCT/type: yes/0
Extra: 01904ef3609e63f41e9293538613272fb3e29b09a441ab7e8b705d92c4cd56a25f02110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f862cefe0ae47694054f0d82ed0c417c16f5ff2abfd782dc5553017b739c719 0.600000000000 1372311 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": 914961, "vin": [ { "gen": { "height": 914951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f862cefe0ae47694054f0d82ed0c417c16f5ff2abfd782dc5553017b739c719" } } ], "extra": [ 1, 144, 78, 243, 96, 158, 99, 244, 30, 146, 147, 83, 134, 19, 39, 47, 179, 226, 155, 9, 164, 65, 171, 126, 139, 112, 93, 146, 196, 205, 86, 162, 95, 2, 17, 0, 0, 0, 11, 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