Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e2cf3d324b8859d2fb76e1f0c64fb23344e1c949498eec2a87fd207383c0289

Tx prefix hash: 53f62d678232a51b873c9179e46a7cf49e39928df8c085ce9c7344d32918a6e4
Tx public key: 24977aa3abb06e4834c49b07830d00abd296533187b48f523e55c68b06c3a90f
Timestamp: 1725209426 Timestamp [UCT]: 2024-09-01 16:50:26 Age [y:d:h:m:s]: 00:171:19:01:47
Block: 1100742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122595 RingCT/type: yes/0
Extra: 0124977aa3abb06e4834c49b07830d00abd296533187b48f523e55c68b06c3a90f021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19c1d37990846be2e2f3899cdae51d6506c783d2975900c578fac21f8232f846 0.600000000000 1576723 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": 1100752, "vin": [ { "gen": { "height": 1100742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19c1d37990846be2e2f3899cdae51d6506c783d2975900c578fac21f8232f846" } } ], "extra": [ 1, 36, 151, 122, 163, 171, 176, 110, 72, 52, 196, 155, 7, 131, 13, 0, 171, 210, 150, 83, 49, 135, 180, 143, 82, 62, 85, 198, 139, 6, 195, 169, 15, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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