Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3892e12b0cf47b5624517cf4d618bfcd8d4d2f804e781ac5aa1ce3dbc5748bf6

Tx prefix hash: e77e5c5d44f71a5966ff736e40427cb765aeef45ee86f61c6df7882d65ce8dd2
Tx public key: ace8ee401a4afc987511d63284fe5a8679c2f817514820c81c5d964cedae4fc9
Timestamp: 1707716231 Timestamp [UCT]: 2024-02-12 05:37:11 Age [y:d:h:m:s]: 00:314:14:07:45
Block: 955707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225259 RingCT/type: yes/0
Extra: 01ace8ee401a4afc987511d63284fe5a8679c2f817514820c81c5d964cedae4fc90211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9f104c09e71814d26363ba94cb4f032960971389f68c301010727df54a46aa9 0.600000000000 1415005 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": 955717, "vin": [ { "gen": { "height": 955707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9f104c09e71814d26363ba94cb4f032960971389f68c301010727df54a46aa9" } } ], "extra": [ 1, 172, 232, 238, 64, 26, 74, 252, 152, 117, 17, 214, 50, 132, 254, 90, 134, 121, 194, 248, 23, 81, 72, 32, 200, 28, 93, 150, 76, 237, 174, 79, 201, 2, 17, 0, 0, 0, 3, 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