Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 776022b64160f537b1187b62ed586763c2e7c78f44ce2bd92d88698839469c0b

Tx prefix hash: f818f9917acae5f84c27baf03534f0f56def278370efcd33a1de1f8247d093b5
Tx public key: 4747e51de7810cd40ae20c968e90ad505d57254d6ed8f1a9f09061e8f8fb4b72
Timestamp: 1731983368 Timestamp [UCT]: 2024-11-19 02:29:28 Age [y:d:h:m:s]: 01:001:11:28:40
Block: 1156816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259460 RingCT/type: yes/0
Extra: 014747e51de7810cd40ae20c968e90ad505d57254d6ed8f1a9f09061e8f8fb4b72021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efa377f9ab4f564c9c5e59c2bb1b5e165fbef7bca1020891d95ca397ecb7511e 0.600000000000 1642439 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": 1156826, "vin": [ { "gen": { "height": 1156816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efa377f9ab4f564c9c5e59c2bb1b5e165fbef7bca1020891d95ca397ecb7511e" } } ], "extra": [ 1, 71, 71, 229, 29, 231, 129, 12, 212, 10, 226, 12, 150, 142, 144, 173, 80, 93, 87, 37, 77, 110, 216, 241, 169, 240, 144, 97, 232, 248, 251, 75, 114, 2, 17, 0, 0, 0, 4, 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