Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfdbad665e345ccf9c0f90930d4d79180de49325e80abd67f7f8172c712f48f9

Tx prefix hash: 8f68ae3d71f74b405ea19ffeeed33407eed81db477142228368dca3af8722e7f
Tx public key: 2142b0e2e32b7cc20e2d1d21cf662b571df19b11413ed6335a6f65e2217348c4
Timestamp: 1725827865 Timestamp [UCT]: 2024-09-08 20:37:45 Age [y:d:h:m:s]: 00:123:07:22:16
Block: 1105874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88180 RingCT/type: yes/0
Extra: 012142b0e2e32b7cc20e2d1d21cf662b571df19b11413ed6335a6f65e2217348c402110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19c9f8a75af90e224da7c90a59b2e33197b64fcd17291e5c9ca541da4caf900e 0.600000000000 1583363 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": 1105884, "vin": [ { "gen": { "height": 1105874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19c9f8a75af90e224da7c90a59b2e33197b64fcd17291e5c9ca541da4caf900e" } } ], "extra": [ 1, 33, 66, 176, 226, 227, 43, 124, 194, 14, 45, 29, 33, 207, 102, 43, 87, 29, 241, 155, 17, 65, 62, 214, 51, 90, 111, 101, 226, 33, 115, 72, 196, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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