Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b41022d2d6538bf9366d776f2e9fc72ffa540bdbfc4d2606648162b902783e2

Tx prefix hash: 2feb66b051e1a5135a4b7339a41e2d0ab16b04b2934eddc692fb7bd2ebe20db0
Tx public key: 1b0711e66889cf8c8c84fbf84e49abd3c113020816d4bbe41ffa59a536ea3661
Timestamp: 1697743562 Timestamp [UCT]: 2023-10-19 19:26:02 Age [y:d:h:m:s]: 01:176:06:12:28
Block: 873241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386985 RingCT/type: yes/0
Extra: 011b0711e66889cf8c8c84fbf84e49abd3c113020816d4bbe41ffa59a536ea366102110000000533af99f4000000000000000000

1 output(s) for total of 0.784494838000 dcy

stealth address amount amount idx
00: cabd67ca8eef31b6b9cd4036467084bbe36565fb0df3f3d73c8be5e82c430a77 0.784494838000 1328375 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": 873251, "vin": [ { "gen": { "height": 873241 } } ], "vout": [ { "amount": 784494838, "target": { "key": "cabd67ca8eef31b6b9cd4036467084bbe36565fb0df3f3d73c8be5e82c430a77" } } ], "extra": [ 1, 27, 7, 17, 230, 104, 137, 207, 140, 140, 132, 251, 248, 78, 73, 171, 211, 193, 19, 2, 8, 22, 212, 187, 228, 31, 250, 89, 165, 54, 234, 54, 97, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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