Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e80bc9d70c480cef392f5076595761e754f4ee5ad31be9adb78134f9dd3c423d

Tx prefix hash: cf54748c02e11f591b88dd271a8e73559b2e20729f911137168fe5bd7b8c7ab5
Tx public key: 7e1a4d67d510e5fba35c131e3b5ae2f2be66f04a2b3545f00a406db86dac55e8
Timestamp: 1733498067 Timestamp [UCT]: 2024-12-06 15:14:27 Age [y:d:h:m:s]: 00:335:18:55:31
Block: 1169354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237508 RingCT/type: yes/0
Extra: 017e1a4d67d510e5fba35c131e3b5ae2f2be66f04a2b3545f00a406db86dac55e8021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efb1f1fba15589d72a698bbe31f1497e06f6b9bfcb2b4c446fad3ec938ebd1ba 0.600000000000 1655069 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": 1169364, "vin": [ { "gen": { "height": 1169354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efb1f1fba15589d72a698bbe31f1497e06f6b9bfcb2b4c446fad3ec938ebd1ba" } } ], "extra": [ 1, 126, 26, 77, 103, 213, 16, 229, 251, 163, 92, 19, 30, 59, 90, 226, 242, 190, 102, 240, 74, 43, 53, 69, 240, 10, 64, 109, 184, 109, 172, 85, 232, 2, 17, 0, 0, 0, 7, 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