Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8ec686cd53d921f7e0763726b2a4f215cf803d2d34ce74ee3abd339634179a0

Tx prefix hash: 6d1cdabf3d9fd4f96bfb82933b0ecc106cf778f6c0d3562704b6081c7e9f5c26
Tx public key: 42873d0136e2ac07944d105b3b817aae29f745b5caf7c58f2c29b47ef4d86395
Timestamp: 1714898276 Timestamp [UCT]: 2024-05-05 08:37:56 Age [y:d:h:m:s]: 00:357:15:21:36
Block: 1015268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255660 RingCT/type: yes/0
Extra: 0142873d0136e2ac07944d105b3b817aae29f745b5caf7c58f2c29b47ef4d863950211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 111679e3617e5c5e7c29f4a433345fdb957ffbf7752a68e9652bbd06a91c0186 0.600000000000 1478583 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": 1015278, "vin": [ { "gen": { "height": 1015268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "111679e3617e5c5e7c29f4a433345fdb957ffbf7752a68e9652bbd06a91c0186" } } ], "extra": [ 1, 66, 135, 61, 1, 54, 226, 172, 7, 148, 77, 16, 91, 59, 129, 122, 174, 41, 247, 69, 181, 202, 247, 197, 143, 44, 41, 180, 126, 244, 216, 99, 149, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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