Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 104a54cde88712cd500038454f2e5c4b657926d60619d557f171c2b8878a82d7

Tx prefix hash: 04fe17d4f5a80815eceb2f2757172acf21057cff962fa25b7f372c54beeaab0b
Tx public key: e5e3c0527965c8e8c43a07849ee88055bb33ae41f2a1bd5b241aa9547c1ee7b1
Timestamp: 1704537601 Timestamp [UCT]: 2024-01-06 10:40:01 Age [y:d:h:m:s]: 01:082:10:15:27
Block: 929342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320026 RingCT/type: yes/0
Extra: 01e5e3c0527965c8e8c43a07849ee88055bb33ae41f2a1bd5b241aa9547c1ee7b10211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64658fcf5e70ad5088f2709e282ea472a0e797260be8e0f7680ad783f691b5ea 0.600000000000 1387214 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": 929352, "vin": [ { "gen": { "height": 929342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64658fcf5e70ad5088f2709e282ea472a0e797260be8e0f7680ad783f691b5ea" } } ], "extra": [ 1, 229, 227, 192, 82, 121, 101, 200, 232, 196, 58, 7, 132, 158, 232, 128, 85, 187, 51, 174, 65, 242, 161, 189, 91, 36, 26, 169, 84, 124, 30, 231, 177, 2, 17, 0, 0, 0, 3, 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