Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7c773d388887ac43eafdc53b49dc33ad0638d5f22e8b88b19e3c4f754bcf548

Tx prefix hash: 40773c4c07f2c7ce5ff4ee0f800852c1387bed67b6dd8f56499e2cdc419e72fc
Tx public key: eba11b7eab70977ec02e8c5023767429be8dd4a5f3e9cd6ca8dd321341eec981
Timestamp: 1722289967 Timestamp [UCT]: 2024-07-29 21:52:47 Age [y:d:h:m:s]: 00:117:15:41:39
Block: 1076533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84183 RingCT/type: yes/0
Extra: 01eba11b7eab70977ec02e8c5023767429be8dd4a5f3e9cd6ca8dd321341eec981021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0659bc4a320bfbb9c7dcaa36a47bba579dee41bdcbbc8f9378d6f8b7718e8da9 0.600000000000 1549072 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": 1076543, "vin": [ { "gen": { "height": 1076533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0659bc4a320bfbb9c7dcaa36a47bba579dee41bdcbbc8f9378d6f8b7718e8da9" } } ], "extra": [ 1, 235, 161, 27, 126, 171, 112, 151, 126, 192, 46, 140, 80, 35, 118, 116, 41, 190, 141, 212, 165, 243, 233, 205, 108, 168, 221, 50, 19, 65, 238, 201, 129, 2, 17, 0, 0, 0, 4, 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