Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96cb5bc9c18f080b6873ce76e2a57bd09b08ad68b39275ddaae39f823ca9f6e6

Tx prefix hash: 20f054fc6d5ee74bda919c7da3a6a83ac4442d08bf06d7202367243fe21e70a3
Tx public key: fad3940919522ae93b7cf900492dfff5c5ec3bef12960074f5c352bea9947d5a
Timestamp: 1705540209 Timestamp [UCT]: 2024-01-18 01:10:09 Age [y:d:h:m:s]: 01:005:22:48:19
Block: 937656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265541 RingCT/type: yes/0
Extra: 01fad3940919522ae93b7cf900492dfff5c5ec3bef12960074f5c352bea9947d5a02110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2404fc7f39400d4f72b0c00553f8a9755016d8bf9c6475f8742d2ceb31f2ecc8 0.600000000000 1395718 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": 937666, "vin": [ { "gen": { "height": 937656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2404fc7f39400d4f72b0c00553f8a9755016d8bf9c6475f8742d2ceb31f2ecc8" } } ], "extra": [ 1, 250, 211, 148, 9, 25, 82, 42, 233, 59, 124, 249, 0, 73, 45, 255, 245, 197, 236, 59, 239, 18, 150, 0, 116, 245, 195, 82, 190, 169, 148, 125, 90, 2, 17, 0, 0, 0, 13, 122, 156, 244, 199, 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