Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1372694d7309a95cb80458d5c9d21f3208e8e0c4a7a68c53f48860b673af5509

Tx prefix hash: 7dd2d4d040a34e534d124431c54508e2be5fbc3b869ac3b51a5bb9f79c827d36
Tx public key: f46a3aff03fc78948d224c065eccb8a3dbe29933f6ed785bc43c9ee9c7218785
Timestamp: 1733378743 Timestamp [UCT]: 2024-12-05 06:05:43 Age [y:d:h:m:s]: 00:132:05:42:00
Block: 1168369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94320 RingCT/type: yes/0
Extra: 01f46a3aff03fc78948d224c065eccb8a3dbe29933f6ed785bc43c9ee9c7218785021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64f5f2b901a0db779fc555b7bea387bdd30365d4f81d1f3802f4c008fd7ced95 0.600000000000 1654078 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": 1168379, "vin": [ { "gen": { "height": 1168369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64f5f2b901a0db779fc555b7bea387bdd30365d4f81d1f3802f4c008fd7ced95" } } ], "extra": [ 1, 244, 106, 58, 255, 3, 252, 120, 148, 141, 34, 76, 6, 94, 204, 184, 163, 219, 226, 153, 51, 246, 237, 120, 91, 196, 60, 158, 233, 199, 33, 135, 133, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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