Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b43bcbec4998b0e3b5b819c438833aa3caf24503a68ad8336f2da6e44f27e91c

Tx prefix hash: ec51a52e3c5f63a478daead382098afb9bfec4d667ff76b79e5df57e1b756e79
Tx public key: 567e6de767f68f68aad5c2f82d3c2b8c09c33584413801320a8b693b3f92ca66
Timestamp: 1749806304 Timestamp [UCT]: 2025-06-13 09:18:24 Age [y:d:h:m:s]: 00:204:19:10:53
Block: 1304050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144179 RingCT/type: yes/0
Extra: 01567e6de767f68f68aad5c2f82d3c2b8c09c33584413801320a8b693b3f92ca66021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff036bfcd782c948db0e26089e87aec16cebd4308420e2dd565f3aeb0f29014d 0.600000000000 1791635 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": 1304060, "vin": [ { "gen": { "height": 1304050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff036bfcd782c948db0e26089e87aec16cebd4308420e2dd565f3aeb0f29014d" } } ], "extra": [ 1, 86, 126, 109, 231, 103, 246, 143, 104, 170, 213, 194, 248, 45, 60, 43, 140, 9, 195, 53, 132, 65, 56, 1, 50, 10, 139, 105, 59, 63, 146, 202, 102, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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