Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9598c88273721838a1dc6c22f0b8a943bdefa2ae54563dc8922f840aa8e13ed0

Tx prefix hash: 867c5fa5eb7472c1b17157e04888f11516d15597172ca3f3866604d4eebff6b3
Tx public key: 1dc79c10c9977881dc0b4c264c3f2601ebf456b8ff6fc7f13f9109248cf967be
Timestamp: 1731186211 Timestamp [UCT]: 2024-11-09 21:03:31 Age [y:d:h:m:s]: 00:014:09:31:43
Block: 1150211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10293 RingCT/type: yes/0
Extra: 011dc79c10c9977881dc0b4c264c3f2601ebf456b8ff6fc7f13f9109248cf967be021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2c79af997793bc64f321ff9bc53cef36775e056e9d7043f76f4f9c26684e1cb 0.600000000000 1635456 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": 1150221, "vin": [ { "gen": { "height": 1150211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2c79af997793bc64f321ff9bc53cef36775e056e9d7043f76f4f9c26684e1cb" } } ], "extra": [ 1, 29, 199, 156, 16, 201, 151, 120, 129, 220, 11, 76, 38, 76, 63, 38, 1, 235, 244, 86, 184, 255, 111, 199, 241, 63, 145, 9, 36, 140, 249, 103, 190, 2, 17, 0, 0, 0, 1, 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