Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbf0b6c8b5b22ead59caa355b437bcd25bd4b3863b43e402556ad79f79b443d1

Tx prefix hash: 0099285c618ef7fe5c8e15e2e92f6ef086b9fdc0d2ceb3ddb4d69157303a98f0
Tx public key: 5da10cfd7782cdb574d669179ea35bd79dc365bb181ec14e7ce748584074b40e
Timestamp: 1739226216 Timestamp [UCT]: 2025-02-10 22:23:36 Age [y:d:h:m:s]: 00:331:14:17:36
Block: 1216521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234818 RingCT/type: yes/0
Extra: 015da10cfd7782cdb574d669179ea35bd79dc365bb181ec14e7ce748584074b40e0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 759f44bb390676ee4beb1ea1d9d1c19e3b0b2e52c01dd230f72922f6f8771f4b 0.600000000000 1703326 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": 1216531, "vin": [ { "gen": { "height": 1216521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "759f44bb390676ee4beb1ea1d9d1c19e3b0b2e52c01dd230f72922f6f8771f4b" } } ], "extra": [ 1, 93, 161, 12, 253, 119, 130, 205, 181, 116, 214, 105, 23, 158, 163, 91, 215, 157, 195, 101, 187, 24, 30, 193, 78, 124, 231, 72, 88, 64, 116, 180, 14, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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